Publish formality core #151
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe the compiler team procedures could be useful as inspiration https://github.com/rust-lang/compiler-team/blob/master/content/procedures/crates.md but it hasn’t been updated in a long while and could be out-of-date. (in particular I don't think it mentions publishing specifically, but could/should be the same as to r+ and admins) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes needed to publish formality-macros and formality-core to crates.io (done!). I want to be able to experiment with these for other languages. Eventually I'd like to publish all of a-mir-formality, just because.
I made the types team owners of these crates, but are there other owners I should add? I expect so, I didn't see obvious docs on forge.